home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
PsL Monthly 1993 December
/
PSL Monthly Shareware CD-ROM (December 1993).iso
/
prgmming
/
dos
/
pascal
/
btr_oop.exe
/
README.DOC
< prev
next >
Wrap
Text File
|
1991-06-03
|
3KB
|
52 lines
The first copy I put up here was missing Global.pas. Sorry I always forget
the trivial stuff. Details,details...
Another difference from the original version is that I have eliminated the
need to specify the Key Index in the calls. Use SetKeyIndx method to do
this now. Note that in proper oops form there should also be a GetKeyIndx
etc.
This is a first cut at an oops version of a Btrieve interface. The idea is
to be able to have a Btrieve FIle that knows how to operate on itself. This
is my first real creative experience with OOPS and I'm sure the code could
use a lot of improvement. In fact the whole concept might be wrong.
I'm putting this up here for feed back.
BTRV.PAS - Pretty much just the interface shipped by Novell for TP.
The only difference is that the position block was no longer
needed as part of the BTRV function call since each instance
can keep track of it's own instance.
BTRV_IO.PAS - Is the first decendent which attempts to give a more
programmer fiendly interface. I was really amazed at how things
simplified in the oops version. About the only thing even
somewhat tricky is the pointer usage to the DataBuffer area.
I'm really not sure I did this the best way.
I have not implemented any of the extended btrieve calls.
Actually its beyond me as to how you would implement these
at the level of this method. Certainly you could could create
the function at this level but it wouldn't do much. The
trick to extended calls is the definition of the data buffer
on send and recieve. This would be very specific to the
derived instance. All of the work for the extended call would
need, in this case, be in CPU_OBJ.
CPU_OBJ,
TEST - Example of the interface usage. This program does nothing on the
screen when you run it but you can execute it in IDE and step
through with watches on things like PCpu^.Fld and Status to make
sure things are working as intended. MAKE SURE you set the path
in the open call to where ever you stashed CPU.DMF
CPU.DMF - A Btrieve data file to go with TEST.
Btrieve Programmers Please Respond.
Manny R. 76004, 3107
Distributed by Public (software) Library.
For a catalog of more than 3000 disks of pd/shareware, call 1-800-2424-PSL
or write Public (software) Library, P.O.Box 35705, Houston, TX 77235-5705.